Skip to main content
TrustRadius
SolarWinds Loggly

SolarWinds Loggly

Overview

What is SolarWinds Loggly?

Loggly is a cloud-based log management service provider. It does not require the use of proprietary software agents to collect log data. The service uses open source technologies, including ElasticSearch, Apache Lucene 4 and Apache Kafka.

Read more
Recent Reviews

TrustRadius Insights

Loggly has proven to be an invaluable tool for a wide range of use cases, allowing users to effectively troubleshoot and prevent issues. …
Continue reading

Loggly rocks

8 out of 10
December 15, 2020
Incentivized
Loggly is a neat a straight forward product. We use to centralize most of our application and security logs, including WAF data which we …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing

Standard

$79

Cloud
per month/billed annually

Pro

$159

Cloud
per month/billed annually

Enterprise

$279

Cloud
per month/billed annually

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://www.loggly.com/plans-and-pricing

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Details

What is SolarWinds Loggly?

Unified Log Analysis and Log Monitoring

With environments spanning on-premises, hybrid, and public cloud environments, IT operations and application teams are inundated with unrelated events, issues, and logs. Every outage or slowdown directly impacts the business, either in lost productivity or lost revenue. Issues must be diagnosed rapidly and resolved across all the dynamically changing components underpinning your heterogeneous web applications, services, and infrastructure.

SolarWinds® Loggly® is presented by the vendor as a cost-effective, hosted, and scalable full-stack, multi-source log management solution combining powerful search and analytics with comprehensive alerting, dashboarding, and reporting to proactively identify problems and significantly reduce Mean Time to Repair (MTTR).

SolarWinds Loggly Features

  • Supported: Highly responsive search at scale
  • Supported: Interactive shareable dashboards
  • Supported: Anomaly detection and alerts
  • Supported: Dynamic Field Explorer™
  • Supported: Rapidly pinpoint bottlenecks and failure points
  • Supported: Collaborate with all stakeholders
  • Supported: New shared agent that collects metrics and logs
  • Supported: Add trace context to your logs

SolarWinds Loggly Screenshots

Screenshot of Streamlined Log AnalysisScreenshot of Monitoring & AlertingScreenshot of Screenshot of Screenshot of

SolarWinds Loggly Integrations

SolarWinds Loggly Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Supported CountriesAll
Supported LanguagesEnglish, Spanish

Frequently Asked Questions

Loggly is a cloud-based log management service provider. It does not require the use of proprietary software agents to collect log data. The service uses open source technologies, including ElasticSearch, Apache Lucene 4 and Apache Kafka.

Splunk Enterprise, Sumo Logic, and Rapid7 InsightOps are common alternatives for SolarWinds Loggly.

Reviewers rate Usability highest, with a score of 7.8.

The most common users of SolarWinds Loggly are from Small Businesses (1-50 employees).

SolarWinds Loggly Customer Size Distribution

Consumers0%
Small Businesses (1-50 employees)25%
Mid-Size Companies (51-500 employees)50%
Enterprises (more than 500 employees)25%
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(79)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Loggly has proven to be an invaluable tool for a wide range of use cases, allowing users to effectively troubleshoot and prevent issues. With its syslog digest capabilities, users can sift through logs to identify the root cause of outages and errors, creating alerts for future prevention. By serving as an aggregation point for streaming logs from network access switches and core routers, Loggly efficiently manages large volumes of data. This makes it a valuable tool for support and engineering teams, providing alerting, monitoring, and issue triage solutions. Additionally, Loggly acts as a central repository for logs from PHP-based apps and servers, offering reports, analysis, and aggregation from different sources. Its flexibility extends to monitoring and debugging large-scale application platforms leveraging multiple microservices. By providing detailed information across different environments, Loggly enables efficient issue tracking and resolution. It also aids in meeting auditing requirements by logging network activity and providing proof of network monitoring. Furthermore, Loggly is widely used to troubleshoot systems, gain insights into performance and health, and visualize trends through its dashboard and alarm capabilities. Whether it's monitoring web traffic, capturing logs to identify security threats on internal and external websites, or monitoring integrations between websites and APIs, Loggly proves to be an essential tool in enhancing monitoring capabilities. Its ability to capture the behavior of software applications during development allows for easier investigation and setting up alerts to prevent service disruptions. Loggly is considered a modern platform for log-file analysis due to its compatibility with Linux systems, plaintext config files, utilization of web standards, and open-source friendly nature. Overall, Loggly plays a crucial role in troubleshooting server and application issues by providing effective solutions for resolving problems.

Intuitive and Easy to Use Interface: Users consistently praise Loggly's intuitive and easy-to-use interface, stating that it simplifies tasks and makes them easier to perform. The user-friendly design allows for quick navigation and access to log data, enhancing overall usability.

Highly Effective Alerting System: Many users appreciate the flexibility and effectiveness of Loggly's alerting system, finding it easy to set up alerts for specific events. Notifications can be received through email or Slack, ensuring that users stay informed about critical issues in their applications.

Comprehensive Integration Options: Reviewers value the extensive integration options provided by Loggly, which support a wide range of log sources and platforms. This feature enables users to consolidate logs from different sources into a centralized location for monitoring and analyzing data effectively.

Confusing User Interface: Many users have expressed frustration with Loggly's user interface, stating that it is confusing and difficult to navigate. They find it challenging to perform tasks effectively due to this issue, which negatively impacts their overall experience with the platform.

Cumbersome Query Language: Some users have found Loggly's query language to be cumbersome and unintuitive. They believe that using the query language adds unnecessary complexity to their log analysis process, making it more time-consuming and challenging to extract meaningful insights from their logs.

Difficulty in Sending Logs: Several users have encountered difficulties when trying to send logs to Loggly, particularly depending on the source system they are using and the level of control they have over it. This has caused inconvenience for these users as they face challenges in seamlessly integrating their logs into Loggly for effective analysis and monitoring.

Users commonly recommend considering alternatives and exploring other options in addition to Loggly. They suggest looking into different logging and monitoring solutions before making a decision.

Another common recommendation is to ensure the correct data is inputted and to tweak the data sending process if necessary. Users advise being careful with the data that is being sent to Loggly and making any necessary adjustments to improve the accuracy of the logs.

Integrations and tools are also mentioned as important factors to consider. Users suggest looking into the available integrations and using tools to build the desired structure for log management and analysis.

It is worth noting that some users recommend spending time reducing log noise and standardizing the log entry process. They emphasize the importance of streamlining the logs to avoid unnecessary clutter and confusion.

Additionally, users suggest using Fluentd as an adapter to ensure Loggly receives all the necessary information. They find it helpful for ensuring smooth communication between systems.

Having someone knowledgeable who can provide training on Loggly is also recommended by users. They believe that having assistance from an expert can greatly enhance the user experience.

Organizing requests and their results is another recommendation made by users. They find Loggly useful in this regard, as it helps them keep track of their requests and easily access the corresponding results.

While many users find Loggly to be a good initial solution, some mention that costs can increase as usage grows. It is advised to keep this in mind when considering long-term usage of the platform.

Overall, users describe Loggly as an excellent solution for debug log management and analysis. They appreciate its functionality, especially with the addition of the live-tail client. Some users compare Loggly to LogEntries and note that they find Loggly to have better polish.

Attribute Ratings

Reviews

(1-9 of 9)
Companies can't remove reviews or game the system. Here's why
Score 4 out of 10
Vetted Review
Verified User
Incentivized
We needed a well rounded platform to aggregate system logs from all cloud platforms. Loggly provided this and made it easier to quickly troubleshoot issues in the virtual environment and give us a dashboard to view them. Triage of alerts is made easier using the event timeline feature of Loggly and helps to bring down our repair time.
  • Customizable Dashboards
  • Azure integration
  • Webhook integration
  • Cost
  • Speed of support
  • Better searching
  • Better user management
Loggly was not the best solution overall for us to use. It is more for heavily invested Azure and AWS companies. We had one Azure client but they have since moved to on-prem as the costs were to high. With everyone else on prem, it has not been worth it for us to continue to use Loggly. We used other solutions and will continue to that better meet our needs.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
As we provide a PaaS to both internal employees and our partners, SolarWinds Loggly is essential to monitoring and diagnosing our cloud-based infrastructure. It's been essential for both our development team and our IT group to monitor usage and performance while also identifying and resolving any issues that come up.
  • Fast setup and deployment.
  • Very customizable.
  • Searching and sorting relevant data is intuitive.
  • It's not free.
  • Won't run stand-alone on-premises.
  • Doesn't look as slick as some other alternatives.
Loggly is primarily useful for combining logs into one centralized location. The insights that the dashboards provide also allow us to identify bottlenecks between microservices. We've had multiple instances where the ability to filter logs by keywords and seeing multiple servers' logs at the same time helped identify problems immediately. This has saved us days of troubleshooting.
Score 6 out of 10
Vetted Review
Verified User
Incentivized
Loggly is one of the ways that allow us to possibly capture the behavior of our software applications both during development and when they are running live. Our Development Teams can add logging to their code and they and site reliability engineers can investigate when the information is logged. Incident management has set up some alerts against particular messages to possibly warn before potential service disruptions occur.
  • It can log whatever a developer decides to add information about.
  • Zooming in on a particular time frame is helpful.
  • The ability to tag/label events.
  • Once the logging limit is exceeded, there are no logs period. Unexpectedly noisy logs often correlate with services misbehaving and potentially leading to disruption. An outage is an awful time to lose visibility into the entire system of apps. Some ways to bridge this gap would be appreciated.
  • Filtering by tags is not intuitive in the web interface. You may believe that you are performing the same search and filter as last time since the tags entered are the same, however, this is often not the case. The reliable way to know that you have the same filter is to bookmark the URL. This lack of ease in usability results in devs using Loggly less than they could and implementing logs less effectively during development time (since they don't consider themselves likely to view them anyway).
  • Would like to see a way to onboard our less experienced devs to using Loggly effectively.
This is a good choice if you have developers that understand using logging levels appropriately (i.e. not simply blasting every possible piece of information to logs, knowing to use debug and info levels). If you have people who know how to set up alerts based on logs, you can find it very useful also. However, if you are missing a critical mass of this experience and skill level at your organization, you'll find your logs are very noisy and hard to search through for what you want, subsequently degrading devs' enthusiasm for learning and using them. Furthermore, you may often hit your logging limit and lose logs during critical times. Use this solution if you're confident your technical folks are up to speed on effective logging practices.
Score 5 out of 10
Vetted Review
Verified User
Incentivized
My company was looking for a centralized logging platform so we tested with Loggly. It was being used by our IT team to monitor network devices as well as security and by our developers to monitor certain Windows event logs, as well as database logs.
  • Centralized logging: having logging for multiples sites (networks) all under one roof was really nice.
  • Customer support: the customer support was outstanding when we had issues with our deployment of our first nxlog configuration.
  • Ease of use: though there is a small learning curve, once conquered, Loggly becomes a very handy tool when needing to pull up past events or logs.
  • nxlog: having to use another piece of software is a bummer
  • nxlog configuration: the learning curve for nxlog is monumental and not very intuitive
  • 1:1 Alerting: Loggly does not support this which is ultimately why my company is looking elsewhere. The alerting does not mesh well those who want login and logout alerts in real-time
I feel Loggly is designed more for the developer's side of things. Loggly was clunky to implement for network device monitoring and didn't meet our needs when it came to security alerts. Though checking for Windows event logs or any sort of process logs it is a breeze, it did not check all the boxes it needed to for us to implement.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
SolarWinds Loggly is used by our IT Operations as well as the Engineering department. We use it to troubleshoot and monitor our application. It's used to notify the proper people for certain errors and issues.
  • Makes viewing logs more readable.
  • Allows us to pull logs from different sources.
  • Search is good, when you know how to use it.
  • Support is not the best, it's only email and they won't get on a remote session with you.
  • Bit of a learning curve to get started.
  • Had issues with getting CloudWatch logs, had to escalate to a higher support rep.
SolarWinds Loggly is well suited for monitoring application and service logs. Great to track down errors so long as your app exposes them! It does a great job as long as you have the log sources piped through properly. Where it's less appropriate is probably for Windows Security Events, that would be more for a SIEM.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
While Loggly is not technically open-source, it is a modern platform for log-file analysis. Oftentimes, in our projects we will acquire competing DevOps stacks, in order to evaluate their effectiveness for us. Our criteria is usually very simple: 1. Does it work? 2.) Does it work on Linux? 3.) Does it use .config file format, or similar plaintext config files? (we generally try to stay away from XML-based file formats, or proprietary formats (think: binary), due to the overhead, and complexity that we feel does not work for us) 4.) is it modern? (i.e. if there is a UX component to the project, does it employ web-standards, such as NodeJS, HTML5, Angular, et. al) 5. It is open-source friendly? (i.e. is it built with Open Source tools, or is the Licensing less restrictive than Microsoft EULA?) Technical difficulty is almost never a concern for my team.
  • Modern: Loggly is modern: Dashboards, realtime information and the ability speak many different data sources and environments makes it an attractive choice
  • Configurability: Loggly gets log parsing right: by allowing you to in real time- filtering of log data, tagging and identifying data sources
  • DevOps friendly: Loggly is very Componentized: You can have an instance of Loggly running that will Monitor your Linux instance, in addition to all of it's services, as an example. Also, you can start/stop Loggly, without affecting your other components
  • Commodity: Loggly is protected by the company's need to convert Loggly into a retail product. While this is fine for the Company, it may limit individual developers from having immediate access to a product they would otherwise adopt. Therefore, Loggly really is geared towards Companies and Commercial Entities
  • Feature creep: Loggly stands in competition with other packages that are open-sourced. And while this is not bad from a Commercial view point (every needs to eat, right?), it almost automatically makes it a 2nd place package, without adding in a killer feature that adds additional value to Developers and DevOps Analysts
  • Parsing: Sometimes, when working with other packages, you get used to a configuration format. Loggly is not so dissimilar that it's hard to read / write, but it's not a one-to-one with say, Logstash. This is more of an annoyance than a real problem, and if you include putting your files into a Repo, then this is even less an annoyance.
Loggly is a great replacement for LogStash, if your project dictates features that LogStash does not have, that Loggly does (which, I can't really think of).

The only real feature of Loggly that most (myself included) can defend, is its cloud logging. Other than that, Loggly does not offer so many more features that Logstash could not replace.

I am recommending Loggly highly, though because its learning curve is so small, that in a commercial environment, where analysts are exposed to it for the first time will have no trouble wrapping their minds around it, and thus can add it to their resume as a real skill. This is really the only real environment for modern, DevOps based software that's not open source: a commercial environment where a company can absorb the cost, and thus maintain control over their investment, also while allowing its employees the ability to easily do what open source platforms are doing for the individual DevOps Analyst/Developer.
March 11, 2019

Loggly simply works

Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use Loggly to monitor and secure our servers across our portfolio of satellite setups. It is used primarily to manage the typical maintenance of our systems, but has also evolved to become part of our security workflow.
  • Flexible dashboards
  • Ease of initial installation
  • Live feed is useful and allows for quick exploration of incoming issues
  • Initial setup of dashboards has a steep learning curve.
  • I find help and guides to be lacking.
  • I find the subscription offers are not accomodating for all use cases, and should be finer grained to allow for a better price/need match.
Loggly is well suited to alert on typical issues that come up at the server level given the particular software setups that we utilise. We have particular problems that need to be monitored, when these appear we are informed [and can] take action quickly. It is a straightforward function but one that is of high value for us. As we continue to use Loggly we are broadening the points on which monitoring takes place, continuing to expand its value for our operations. I cannot comment on less appropriate scenarios as it fulfills on the core scenario for which we installed it.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Our organization uses Loggly both for our own internal systems as well as for the websites and services that we provide our clients. We funnel all log-type output from every conceivable place into Loggly, and it allows us to search, filter, correlate events, and receive alerts when bad things start to happen. It's become one of our most valuable troubleshooting tools, as well as an increasingly-preventative measure before or as problems arise.
  • Collects logs from pretty much any place you can imagine. Many applications have Loggly integration, many programming languages have Loggly libraries, and pushing other logs into Loggly is easily scriptable and automatable.
  • Searching and filtering is incredibly deep, and often very intuitive. You can drill down through any data set, filtering or searching on any value within that data set.
  • Saved graphs and dashboards are a great way to visualize what's happening without having to read through each log entry.
  • Loggly has a significant learning curve to figure out how to use it. At first, it can be daunting staring at a collection of thousands and thousands of logs wondering how you're supposed to make sense of any of it. The initial onboarding and training experience could be better in my opinion.
  • Loggly's user interface is adequate but does have some room for improvement in my opinion. It is a collection of tools which work well on their own, and which do tie into each other in many ways, but it doesn't feel like there is a good, cohesive, overall workflow to the application. This is a bit vague, but I feel like it needs more of a concept of a "user dashboard" when you log in providing an overview of things like important/flagged recent log entries, detected anomalies, recently tripped alerts, perhaps links to your favorite or most common/recent graph dashboards.
  • There is always room for more integrations and more ways to pull/collect logs. I would love to see Loggly offer a service which periodically pulls updated logs via SFTP, without the need for me to set up an intermediate shell script on a timer.
If you manage a lot of different systems or frequently find you're jumping between different log files or different platforms when troubleshooting an issue or analyzing activity, then Loggly just might be a perfect fit for your needs. If you host one website or service and simply need to keep tabs on the logs for that one site, then Loggly might be overkill. But beyond that, Loggly can certainly save time and headaches.
September 06, 2016

Loggly. A great solution.

Score 5 out of 10
Vetted Review
Verified User
Incentivized
We use Loggly to aggregate all of our log files from all of our different servers, allowing us to have one location where we can go to see everything that is happening. It is being used primarily by the operations department. It allows us to have a centralized place that we don't have to manage that stores and files away all of our logs.
  • Centralized location of logs
  • Great graphs
  • Detailed information
  • Steeper learning curve
  • Many other competitors
Having a centralized location for all log files makes it insanely easy to see long-term trends as well as a great place to go when an incident occurs and you can quickly search through your logs to find the files. Many times when a webserver has an issue, Loggly is the first place I check.
Return to navigation